<h2>General usage advices</h2>
<accordion close-others="true">
  <accordion-group heading="Do you advice to use 32 or 64 bit Eclipse?">
  Update:Due to market praktises 64bit becomes more and more a must. So if you have a 64 bit system and you are sure you have a 64 bit java installed feel free to use 64 bit eclipse.<br/>
    Use 32 bit. No doubth. Why? The benefit of 64 is when you need more than 3Gig of memory to run the Eclipse environment.<br/>
    Unless you integrate your projects with a suite of professional tools you will never hit this limit.<br/>
    Arduino comes with a  set of 32 bit tools. 64 bit Eclipse can not closely integrate with these tools. As a consequence "64 bit alternatives" are delivered with the plugin.<br/>
    However these alternatives sometimes have "side efects".<br/>
    See for instance RTTX library on mac and ubuntu.(fixed in newer versions)<br/>
    Also the tools are not tested by Arduino in 64 bit. This explains  for instance why the serial monitor does not work with Leonardo in 64 bit but it does in 32 bit.<br/>
    So unless you really need 64bit Eclipse I strongly advice 32 bit Eclipse.<br/>
    Update: Arduino started to support 64 bit on Linux so that may be an exception.<br/>

  </accordion-group>
  <accordion-group heading="Are there any restrictions to the project name?">
    Because of the toolchain used folowing characters are changed to '_' when given as project name in the new project wizard : ' '; '(' ; ')'.<br/>
    The tool allows you to use these but they will be replaced.
  </accordion-group>
  <accordion-group heading="What is the best way to work with multiple Arduino boards?">
    You can have all your projects in the same Eclipse workspace. There is no benefit of splitting them over workspaces.
  </accordion-group>
  <accordion-group heading="What is the best way to work with a mixture of boards (Arduino - non Arduino)?">
    From version 1.3 the Eclips eplugin supports multiple board.txt files. If you use this setup there is no reason to seperate the boards into different workspaces<br/>
    You can have all your projects in the same Eclipse workspace. There is no benefit of splitting them over workspaces..
  </accordion-group>
  <accordion-group heading="What is the best way to work with multiple Arduino versions (0022 0023 1.0 1.01)?">
    From V3 onwards you can have mutiple arduino versions in the same workspace.
    This allows for a gradual upgrade process.
    Pre V3:
    Each Arduino version should have its own Eclipse workspace. Changing Arduino version in the plugin may corrupt the plugin settings.
    In V2 I have experimented with creating hardwares that are actually Arduino versions. This works out fine but has the drawback that it is very easy to make mistakes.

  </accordion-group>
  <accordion-group heading="How do you advice to use the Eclipse workspaces?">
    I keep all my Arduino projects in one Eclipse workspace. I make sure they al compile so there are no errors in the problem view.<br/>
    I work this way, and I'm not sure I would advice this way of working.<br/>
    I would advice starting with only one workspace. You may decide not to upgrade all you projects to the latest Arduino version.<br/>
    From V3 onwords even that can be done in one workspace. If you end up with plenty of projects in the same workspace you may find it is easier to split the workspace.<br/>
    Note that eclipse supports closing projects which improves performance.<br/>
    Note that splitting a workspace does not involve plenty of work as Eclipse supports drag and drop.
  </accordion-group>
</accordion>
